home *** CD-ROM | disk | FTP | other *** search
- Path: news.wco.com!news
- From: dbirdman@tidepool.com
- Newsgroups: comp.os.ms-windows.programmer.win32,comp.lang.basic.visual.misc,comp.os.ms-windows.programmer.ole,comp.lang.c++
- Subject: Re: Calling 32-bit DLLs from 16-bit-Applications
- Date: Fri, 02 Feb 1996 19:52:59 GMT
- Organization: West Coast Online's News Server - Not responsible for content
- Message-ID: <4etq1s$7fc@news.wco.com>
- References: <4enu1u$20c_001@adv.magwien.gv.at>
- NNTP-Posting-Host: ts03.tidepool.com
- X-Newsreader: Forte Free Agent 1.0.82
-
- stw@adv.magwien.gv.at (Wolfgang Steiner) wrote:
-
-
- >my problem is following:
- >I must use a 32bit-DLL from Visual Basic 3.0 (a 16bit-application)
- >under WfW (the DLL also runs with Win32s) and Win95.
-
- >Calling the DLL directly doesn't work.
-
- >Which possibilities exist to solve this problem?
-
- >) Writing an own DLL for conversion between 16bit and 32bit?
- > If yes, from where can I get more information about that?
- > Do such DLL's exist anywhere?
-
- There is a public domain thunking .DLL called CALL32.DLL. I have a
- copy available from one of my pages:
- http://www.redshift.com/~arcatpet/vb.html
-
- There are also a couple of VB3 program source code samples there that
- use the .DLL, one for Win95 taskbar tray usage, and another for
- Win95/NT registry reading/writing. Note that internal documentation
- for CALL32.DLL says it will only work on NT, but it was written before
- the WOW in Win95 became compliant with the NT version. No problems
- experienced with Win95 - haven't tested with Win32s.
-
- --
- Don Bradner
- dbirdman@redshift.com
- author of WWPlus, ImgViewer/16, and BirdData
- http://www.redshift.com/~arcatpet
-
-